Network function handling in the context of inter-management function mobility

ABSTRACT

A method for a target mobility management entity and a target mobility management entity for executing the method in a core network to communicate network function (NF) utilization information with a source mobility management entity during a change of mobility management entity are disclosed. The method comprises: receiving at least one old NF identifier (ID) from the source mobility management entity that corresponds to an old NF entity serving a user equipment (UE); determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF entity of a same NF type as the old NF entity; and communicating, to the source mobility management entity, information that indicates to the source mobility management entity whether the target mobility management entity uses the at least one old NF ID or uses the at least one new NF ID.

This application is a continuation of U.S. patent application Ser. No.17/254,935, filed Dec. 22, 2020, which is a 35 U.S.C. § 371 nationalphase filing of International Application No. PCT/EP2019/065623, filedJun. 13, 2019, which claims the benefit of U.S. Provisional ApplicationNo. 62/689,547, filed Jun. 25, 2018, the disclosures of which areincorporated herein by reference in their entireties.

TECHNICAL FIELD

Embodiments presented herein relate to methods, nodes/functionsentities, computer and computer program products for a target mobilitymanagement function in a core network to communicate network function(NF) utilization information with a source mobility management functionduring a change of mobility management function.

BACKGROUND

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features,and advantages of the enclosed embodiments will be apparent from thefollowing description.

3GPP Technical Specification (TS) 23.502 v 15.1.0 has a mobilityregistration procedure with access and mobility management function(AMF) change, where the old (sometimes referred to herein as “source”)AMF may include some network function (NF) identifiers (IDs) (such as,by way of non-limiting example, PCF ID, SMSF ID, or the like) that areused by the user equipment (UE) and are provided to the new (sometimesreferred to herein as “target”) AMF. The new/target AMF will check ifthe previously used NFs are still suitable for the UE and if not, new NFIDs may be selected.

FIG. 1 illustrates the Registration procedure (TS 23.502 v 15.1.0, FIG.4.2.2.2.2-1). Step 5 of the Registration procedure is the following:

-   -   5. [Conditional] old AMF to new AMF: Response to        Namf_Communication_UEContextTransfer (SUPI, UE Context in AMF        (as per Table 5.2.2.2.2-1)).    -   Old AMF responds to the new AMF for the        Namf_Communication_UEContextTransfer invocation by including the        UE's SUPI and MM Context.    -   If old AMF holds information about established PDU Sessions, the        old AMF includes Session Management Function (SMF) information        DNN, S-NSSAI(s) and PDU Session ID.

If old AMF holds information about active NGAP UE-TNLA bindings toN3IWF, the old AMF includes information about the NGAP UE-TNLA bindings.

Step 16 of the Registration procedure is the following:

-   -   16. [Optional] new AMF performs a Policy Association        Establishment as defined in clause 4.16.1.2. For an Emergency        Registration, this step is skipped.    -   If the new AMF contacts the Policy Control Function (PCF)        identified by the (V-)PCF ID received during inter-AMF mobility        in step 5, the new AMF shall include the (V-)PCF ID in the        Npcf_AMPolicyControl Get operation. This indication is not        included by the AMF during initial registration procedure.    -   If the AMF notifies the Mobility Restrictions (e.g. UE location)        to the PCF for adjustment, or if the PCF updates the Mobility        Restrictions itself due to some conditions (e.g. application in        use, time and date), the PCF shall provide the updated Mobility        Restrictions to the AMF.

Step 21 of the Registration procedure is the following:

-   -   21. [Conditional] old AMF to (V-)PCF: AMF-Initiated Policy        Association Termination.    -   If the old AMF previously initiated a Policy Association to the        PCF, and the old AMF did not transfer the PCF ID to the new AMF        (e.g. new AMF is in different PLMN), the old AMF performs an        AMF-initiated Policy Association Termination procedure, as        defined in clause 4.16.3.2, to delete the association with the        PCF.

The AMF establishes the connection/association with PCF (new PCFselected vs PCF re-used) in accordance with the following:

4.16.1 Policy Association Establishment

4.16.1.1 General

There are three cases considered for Policy Association Establishment:

1. UE initial registration with the network.

2. The AMF re-allocation without PCF change in handover procedure andregistration procedure.

3. The AMF re-allocation with PCF change in handover procedure andregistration procedure.

FIG. 2 illustrates the AM Policy Association Establishment with newSelected PCF (TS 23.502 v 15.1.0, FIG. 4.16.1.2-1).

4.16.1.2 AM Policy Association Establishment with new Selected PCF. Thisprocedure concerns the following scenarios:

1. UE initial registration with the network.

2. The AMF re-allocation with PCF change in handover procedure andregistration procedure.

This procedure concerns both roaming and non-roaming scenarios.

FIG. 3 illustrates the Policy Association Establishment with the old PCF(TS 23.502 v 15.1.0, FIG. 4.16.1.3-1).

AM Policy Association Establishment with the Old PCF

The procedure concerns the situation involving AMF relocation withoutPCF change in handover procedure and registration procedure.

This procedure concerns both roaming and non-roaming scenarios.

FIG. 4 illustrates the Registration procedure supporting Short MessageService (SMS) over NAS (TS 23.502 v 15.1.0, FIG. 4.13.3.1-1).

Below is how the AMF manages the connection/association with the SMSF.

4.13.3.2 Deregistration Procedures for SMS Over NAS

If the UE indicates to the AMF that the UE no longer wants to send andreceive SMS over NAS (e.g., not including “SMS supported” indication insubsequent Registration Request message) or if the AMF considers thatthe UE is deregistered or the AMF receives a Deregistration Notificationfrom the UDM indicating UE Initial Registration, Subscription Withdrawnor 5GS to EPS Mobility as specified in clause 5.2.3.2.2 of TS 23.502 v15.1.0, the AMF invokes a Nsmsf_SMService_Deactivate service operationto trigger the release of the UE Context for SMS on SMSF based on localconfigurations. The AMF may delete or deactivate the stored SMSF addressin its UE Context. The SMSF shall invoke a Nudm_UECM_Deregistration(SUPI, NF ID, Access Type) service operation from UDM to trigger the UDMto delete the SMSF address of the UE. The UDM may update the UE contextin SMSF in UDR by Nudr_DM_Update (SUPI, Subscription Data, SMSSubscription data, SMSF address). The SMSF also removes the UE Contextfor SMS, including AMF address.

SUMMARY

There currently exist certain situations when moving from a sourcemobility management function (e.g., a source AMF) to a target mobilitymanagement function (e.g., a target AMF) where it is not defined whetherthe source AMF should terminate associations with NFs or not. Inparticular, when some NFs are selected by an AMF during initiationregistration or initial PDU session establishment, a long-lifeconnection/association will be created between the AMF and the NFs, suchas, by way of non-limiting example, PCF and/or SMSF (SMF change willcome in 3GPP rel-16).

During UE mobility and when a new/target AMF is selected, if theold/source AMF does not provide information related to the selected/oldNFs, i.e. the PCF ID or SMSF ID to the new/target AMF, then it is clear,at least for the PCF case (SMSF change is not named currently in theTS), that the old/source AMF is responsible for connection/associationrelease.

However, in the situation where the old/source AMF provides informationrelated to the selected NFs, such as providing the PCF ID and/or SMSFID, for example, the new/target AMF may decide to either 1) re-use theNFs selected by the old/source AMF, or 2) select new NFs to serve the UEand PDU sessions. However, the long-life connection/association handlingbetween the old/source AMF and the NFs is not clearly specified,regardless of whether the NFs are re-used or new NFs are selected.

Certain aspects of the present disclosure and their embodiments providesolutions to the aforementioned or other challenges.

The solution proposes:

1. A mechanism between the new/target AMF and the old/source AMF, duringan inter-AMF mobility procedure, to allow the new/target AMF to informthe old/source AMF if the NF (e.g., SMSF, PCF, SMF), which were selectedfor the UE and PDU session(s) by the old/source AMF, will be re-used ornot. The target AMF may make a separate indication for each NF, suchthat the target AMF may indicate that some NFs are reused, and othersare not.

2. If not reused, the old/source AMF is responsible for initiating therelease of connection/association of the NFs after being informed by thenew/target AMF.

There are, proposed herein, various embodiments that address one or moreof the issues disclosed herein.

In one embodiment, a method for a target mobility management function ina core network to communicate network function (NF) utilizationinformation with a source mobility management function during a changeof mobility management function is provided. The method includesreceiving, by the target mobility management function, at least one oldNF identifier (ID) from the source mobility management function thatcorresponds to an old network function (NF) serving a user equipment(UE). The method further includes determining to either use the at leastone old NF ID or to use at least one new NF ID that corresponds to a newNF of a same NF type as the old NF. The method further includescommunicating, by the target mobility management function to the sourcemobility management function, information that indicates to the sourcemobility management function whether the target mobility managementfunction uses the at least one old NF ID or uses the at least one new NFID.

In another embodiment, a target mobility management function node forcommunicating network function (NF) utilization information with asource mobility management function node during a change of mobilitymanagement function is provided. The target mobility management functionnode includes one or more processors and includes memory storinginstructions executable by the one or more processors. The targetmobility management function node is operable to perform the method ofreceiving, by the target mobility management function node, at least oneold NF identifier (ID) from the source mobility management function nodethat corresponds to an old network function (NF) serving a userequipment (UE), determining to either use the at least one old NF ID orto use at least one new NF ID that corresponds to a new NF of a same NFtype as the old NF, and communicating, by the target mobility managementfunction node to the source mobility management function node,information that indicates to the source mobility management functionnode whether the target mobility management function node uses the atleast one old NF ID or uses the at least one new NF ID.

In another embodiment, a method for a source mobility managementfunction in a core network to receive network function (NF) utilizationinformation from a target mobility management function during a changeof mobility management function is provided. The method includessending, by the source mobility management function to the targetmobility management function, at least one old NF identifier (ID) thatcorresponds to an old network function (NF) serving a user equipment(UE). The method further includes receiving, by the source mobilitymanagement function from the target mobility management function,information that indicates whether the target mobility managementfunction uses the at least one old NF ID or uses at least one new NF IDthat corresponds to a new NF serving the UE.

In another embodiment, a source mobility management function node forreceiving network function (NF) utilization information from a targetmobility management function node during a change of mobility managementfunction is provided. The source mobility management function nodeincludes one or more processors and includes memory storing instructionsexecutable by the one or more processors, whereby the source mobilitymanagement function node is operable to perform the method of sending,by the source mobility management function node to the target mobilitymanagement function node, at least one old NF identifier (ID) thatcorresponds to an old network function (NF) serving a user equipment(UE), and receiving, by the source mobility management function nodefrom the target mobility management function node, information thatindicates whether the target mobility management function node uses theat least one old NF ID or uses at least one new NF ID that correspondsto a new NF serving the UE.

Certain embodiments may provide one or more of the following technicaladvantage(s).

BRIEF DESCRIPTION OF THE DRAWINGS

The proposed solutions are now described, by way of example, withreference to the accompanying drawings, in which:

FIG. 1 illustrates a Registration procedure;

FIG. 2 illustrates an AM Policy Association Establishment with newSelected PCF;

FIG. 3 illustrates a Policy Association Establishment with an PCF;

FIG. 4 illustrates a Registration procedure supporting SMS over NAS;

FIG. 5 illustrates one example of a cellular communications network 500according to some embodiments of the present disclosure;

FIG. 6 illustrates a wireless communication system represented as anexample 5G network architecture with NFs using point-to-point referencepoints/interfaces;

FIG. 7 illustrates an example of a 5G network architecture usingservice-based interfaces between the NFs in the control plane;

FIG. 8 illustrates a Preparation Phase;

FIG. 9 illustrates an Execution Phase;

FIG. 10 illustrates a General Registration procedure, either for CM-IDLEmode mobility or CM-CONNECTED mode mobility;

FIG. 11 illustrates a Policy Association Establishment procedure with aPCF;

FIG. 12 is a schematic block diagram of a network function node suitablefor implementing a source mobility management function or targetmobility management function according to some embodiments;

FIG. 13 is a schematic block diagram that illustrates a virtualizedembodiment of the network function node 1200 according to someembodiments of the present disclosure;

FIG. 14 is a schematic block diagram of the network function node 1200according to some other embodiments of the present disclosure;

FIG. 15 is a flowchart illustrating a method for a target mobilitymanagement function in a core network to communicate NF utilizationinformation with a source mobility management function during a changeof mobility management function according to one embodiment;

FIG. 16 is a flowchart illustrating a method implemented in a sourcemobility management function in accordance with one embodiment;

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein. The disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art. Radio Node: As used herein, a “radio node” iseither a radio access node or a wireless device.

Radio Access Node: As used herein, a “radio access node” or “radionetwork node” is any node in a radio access network of a cellularcommunications network that operates to wirelessly transmit and/orreceive signals. Some examples of a radio access node include, but arenot limited to, a base station (e.g., a New Radio (NR) base station(gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation(5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LongTerm Evolution (LTE) network), a high-power or macro base station, alow-power base station (e.g., a micro base station, a pico base station,a home eNB, or the like), and a relay node.

Core Network Node: As used herein, a “core network node” is any type ofnode in a core network. Some examples of a core network node include,e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway(P-GW), a Service Capability Exposure Function (SCEF), or the like.

Wireless Device: As used herein, a “wireless device” is any type ofdevice that has access to (i.e., is served by) a cellular communicationsnetwork by wirelessly transmitting and/or receiving signals to a radioaccess node(s). Some examples of a wireless device include, but are notlimited to, a User Equipment device (UE) in a 3GPP network and a MachineType Communication (MTC) device.

Network Node: As used herein, a “network node” is any node that iseither part of the radio access network or the core network of acellular communications network/system.

Note that the description given herein focuses on a 3GPP cellularcommunications system and, as such, 3GPP terminology or terminologysimilar to 3GPP terminology is oftentimes used. However, the conceptsdisclosed herein are not limited to a 3GPP system.

Note that, in the description herein, reference may be made to the term“cell;” however, particularly with respect to 5G NR concepts, beams maybe used instead of cells and, as such, it is important to note that theconcepts described herein are equally applicable to both cells andbeams.

FIG. 5 illustrates one example of a cellular communications network 500according to some embodiments of the present disclosure. In theembodiments described herein, the cellular communications network 500 isa 5G NR network. In this example, the cellular communications network500 includes base stations 502-1 and 502-2, which in LTE are referred toas eNBs and in 5G NR are referred to as gNBs, controlling correspondingmacro cells 504-1 and 504-2. The base stations 502-1 and 502-2 aregenerally referred to herein collectively as base stations 502 andindividually as base station 502. Likewise, the macro cells 504-1 and504-2 are generally referred to herein collectively as macro cells 504and individually as macro cell 504. The cellular communications network500 may also include a number of low power nodes 506-1 through 506-4controlling corresponding small cells 508-1 through 508-4. The low powernodes 506-1 through 506-4 can be small base stations (such as pico orfemto base stations) or Remote Radio Heads (RRHs), or the like. Notably,while not illustrated, one or more of the small cells 508-1 through508-4 may alternatively be provided by the base stations 502. The lowpower nodes 506-1 through 506-4 are generally referred to hereincollectively as low power nodes 506 and individually as low power node506. Likewise, the small cells 508-1 through 508-4 are generallyreferred to herein collectively as small cells 508 and individually assmall cell 508. The base stations 502 (and optionally the low powernodes 506) are connected to a core network 510.

The base stations 502 and the low power nodes 506 provide service towireless devices 512-1 through 512-5 in the corresponding cells 504 and508. The wireless devices 512-1 through 512-5 are generally referred toherein collectively as wireless devices 512 and individually as wirelessdevice 512. The wireless devices 512 are also sometimes referred toherein as UEs.

FIG. 6 illustrates an exemplifying wireless communication systemrepresented as a 5G network architecture composed of core NetworkFunctions (NFs), where interaction between any two NFs is represented bya point-to-point reference point/interface. FIG. 6 can be viewed as oneparticular implementation of the cellular communications network 500 ofFIG. 5 .

Seen from the access side, the 5G network architecture shown in FIG. 6comprises a plurality of User Equipment (UEs) connected to either aRadio Access Network (RAN) or an Access Network (AN) as well as anAccess and Mobility Management Function (AMF). Typically, the R(AN)comprises base stations, e.g. such as evolved Node Bs (eNBs) or 5G basestations (gNBs) or similar. Seen from the core network side, the 5G coreNFs shown in FIG. 6 include a Network Slice Selection Function (NSSF),an Authentication Server Function (AUSF), a Unified Data Management(UDM), an AMF, a Session Management Function (SMF), a Policy ControlFunction (PCF), and an Application Function (AF).

Reference point representations of the 5G network architecture are usedto develop detailed call flows in the normative standardization. The N1reference point is defined to carry signaling between the UE and theAMF. The reference points for connecting between the AN and the AMF andbetween the AN and the UPF are defined as N2 and N3, respectively. Thereis a reference point, N11, between the AMF and the SMF, which impliesthat the SMF is at least partly controlled by the AMF. N4 is used by theSMF and the UPF so that the UPF can be set using the control signalgenerated by the SMF, and the UPF can report its state to the SMF. N9 isthe reference point for the connection between different UPFs, and N14is the reference point connecting between different AMFs, respectively.N15 and N7 are defined since the PCF applies policy to the AMF and theSMF, respectively. N12 is required for the AMF to perform authenticationof the UE. N8 and N10 are defined because the subscription data of theUE is required for the AMF and the SMF.

The 5G core network aims at separating user plane and control plane. Theuser plane carries user traffic while the control plane carriessignaling in the network. In FIG. 6 , the UPF is in the user plane andall other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in thecontrol plane. Separating the user plane and the control planeguarantees that each plane resource will be scaled independently. Italso allows UPFs to be deployed separately from control plane functionsin a distributed fashion. In this architecture, UPFs may be deployedvery close to UEs to shorten the Round Trip Time (RTT) between UEs anddata networks for some applications requiring low latency.

The core 5G network architecture is composed of modularized functions.For example, the AMF and SMF are independent functions in the controlplane. Separated AMF and SMF allow independent evolution and scaling.Other control plane functions like the PCF and the AUSF can be separatedas shown in FIG. 6 . Modularized function design enables the 5G corenetwork to support various services flexibly.

Each NF interacts with another NF directly. It is possible to useintermediate functions to route messages from one NF to another NF. Inthe control plane, a set of interactions between two NFs is defined asservice so that its reuse is possible. This service enables support formodularity. The user plane supports interactions such as forwardingoperations between different UPFs.

FIG. 7 illustrates a 5G network architecture using service-basedinterfaces between the NFs in the control plane, instead of thepoint-to-point reference points/interfaces used in the 5G networkarchitecture of FIG. 6 . However, the NFs described above with referenceto FIG. 6 correspond to the NFs shown in FIG. 7 . The service(s) etc.that a NF provides to other authorized NFs can be exposed to theauthorized NFs through the service-based interface. In FIG. 7 , theservice-based interfaces are indicated by the letter “N” followed by thename of the NF, e.g. Namf for the service-based interface of the AMF andNsmf for the service-based interface of the SMF, etc. The NetworkExposure Function (NEF) and the Network Repository Function (NRF) inFIG. 7 are not shown in FIG. 6 discussed above. However, it should beclarified that all NFs depicted in FIG. 6 can interact with the NEF andthe NRF of FIG. 7 as necessary, though not explicitly indicated in FIG.6 .

Some properties of the NFs shown in FIGS. 6 and 7 may be described inthe following manner. The AMF provides UE-based authentication,authorization, mobility management, etc. A UE even using multiple accesstechnologies is basically connected to a single AMF because the AMF isindependent of the access technologies. The SMF is responsible forsession management and allocates Internet Protocol (IP) addresses toUEs. It also selects and controls the UPF for user plane data transfer.If a UE has multiple sessions, different SMFs may be allocated to eachsession to manage them individually and possibly provide differentfunctionalities per session. The AF provides information on the packetflow to the PCF responsible for policy control in order to supportQuality of Service (QoS). Based on the information, the PCF determinespolicies about mobility and session management to make the AMF and SMFoperate properly. The AUSF supports authentication function for UEs orsimilar and thus stores data for authentication of UEs or similar whilethe UDM stores subscription data of the UE. The Data Network (DN), notpart of the 5G core network, provides Internet access or operatorservices and similar.

An NF may be implemented either as a network element on a dedicatedhardware, as a software instance running on a dedicated hardware, or asa virtualized function instantiated on an appropriate platform, e.g., acloud infrastructure. The NFs UPF, AMF, SMF, PCF, AF, AUSF, and UDM arespecific examples of a User Plane (UP) entity, a Mobility Management(MM) entity, a Session Management (SM) entity, a Policy and Charging(PC) entity, an Application entity, an Authentication Server entity anda Unified Data Management entity respectively.

The embodiments enhance communication between a source mobilitymanagement function, such as, by way of non-limiting example, a sourceaccess and mobility management function (AMF), and a target mobilitymanagement function, such as by way of non-limiting example, a targetAMF, during a change from the source mobility management function to thetarget mobility management function. The change, for example, may be ahandover. The target mobility management function informs the sourcemobility management function whether old network functions that wereused by the source mobility management function will be used by thetarget mobility management function, or whether new network functionswill be used. If new network functions are being used the targetmobility management function, the source mobility management functionmay perform one or more acts to dissociate from the previous networkfunctions.

The embodiments have applicability in a wide range of applications,including, by way of non-limiting example, the standards TS 23.501 andTS 23.502.

In one embodiment, during a CM-IDLE/CM-CONNECTED mode mobility with AMFchange, a new/target AMF shall indicate to an old/source AMF if any oldNF has been re-used or wherein new NFs have been selected for the UE inthe following AMF services, in case the old AMF has provided informationthat identifies old NFs for the UE.

In one embodiment, the Namf_Communication_RegistrationCompleteNotifyservice operation may be modified in the following manner to supportcommunications between the target AMF and the source AMF regardingwhether a new NF has been selected or old NFs are being utilized.

5.2.2.2.3 Namf_Communication_ReqistrationCompleteNotify ServiceOperation

Service operation name: Namf_Communication_RegistrationCompleteNotify

-   -   Description: This service operation is used by the consumer NF        to inform the AMF that a prior UE context transfer has resulted        in the UE successfully registering with it. The UE context is        marked inactive in the AMF.    -   NOTE 1: This notification corresponds to an implicit        subscription.    -   Input, Required: 5G-GUTI, Reason.    -   Input, Optional: PDU Session ID(s) (indicates the PDU Session(s)        to be released), [IN ONE EMBODIMENT, THIS INFORMATION MAY BE        EXPANDED TO INCLUDE: NF change related indications (such as, by        way of non-limiting example, that a new PCF/SMSF has been        selected or that the old PCF/SMSF is being re-used).]    -   Output, Required: None.    -   Output, Optional: None.    -   See clause 4.2.2.2.2 step 10 for example usage of this service        operation. When the consumer NF (AMF) receives this        notification, it marks the UE context information as inactive        since the UE context has been successfully transferred to the        peer NF and the UE has successfully registered there. The AMF        sends a Namf_Communication_TransferComplete ack to the consumer        NF.

In one embodiment, the Namf_Communication_N2InfoNotify service operationmay be modified in the following manner to support communicationsbetween the target (new) AMF and the source (old) AMF regarding whethera new NF has been selected or old NFs are being utilized.

5.2.2.2.10 Namf_Communication_N2InfoNotify Service Operation

Service operation name: Namf_Communication_N2InfoNotify.

-   -   Description: The AMF uses this service operation to notify a        particular N2 message information towards the NFs that have        subscribed (implicitly or explicitly) for the specific        information.    -   Input, Required: AMF ID (GUAMI), N2 information.    -   Input, Optional: [IN ONE EMBODIMENT, THIS INFORMATION MAY BE        EXPANDED TO INCLUDE: NF change-related indications (such as, by        way of non-limiting example, that a new PCF/SMSF has been        selected or that the old PCF/SMSF is being re-used).] Session ID        (e.g. PDU Session ID) if the N2 information notified is related        to a session (e.g. PDU Session).    -   Output, Required: None.    -   Output, Optional: None.

In one embodiment, the Namf_Communication_CreateUEContext serviceoperation may be modified in the following manner to supportcommunications between the target (new) AMF and the source (old) AMFregarding whether a new NF has been selected or old NFs are beingutilized.

5.2.2.2.11 Namf_Communication_CreateUEContext Service Operation

Service operation name: Namf_Communication_CreateUEContext

-   -   Description: This service operation is used by an old AMF to        create the UE context in a new AMF during handover procedures.    -   Input, Required: 5G-GUTI, UE context of the identified UE. As        described in Table 5.2.2.2.2-1, the UE context may include the        SUPI, DRX parameters, AM policy information, PCF ID, UE network        capability, used N1 security context information, event        subscriptions by other consumer NF, and the list of SM PDU        Session IDs along with the SMF handling the PDU Session, N2        information including source to target RAN transparent        container, Endpoint information of S-AMF to receive N2        information notification about handover complete.    -   Input, Optional: allocated EBI information, PCF ID.    -   Output, Required: Cause, N2 information including Target to        Source transparent container, N2 SM information (PDU Sessions        failed to be setup list, and the N3 DL forwarding information),        handle for the UE context created, [IN ONE EMBODIMENT, THIS        INFORMATION MAY BE EXPANDED TO INCLUDE: NF change-related        indications (i.e. a new SMF has been selected or an old SMF is        re-used).]    -   Output, Optional: None.    -   Note: in case of HO, New changes can either be made in        5.2.2.2.10 (more suitable if the NF is PCF or SMSF) or in        5.2.2.2.11 (more suitable if the NF is SMF)

The above service operations may be used in various procedures,including, for example, the preparation phase and the execution phase ofthe hand over procedure, for CM-CONNECTED mode mobility.

FIG. 8 illustrates the 4.9.1.3.2 Preparation Phase. In support of theembodiments, Step 12 of the Preparation Phase may be updated toincluding the following:

12. [Conditional] T-AMF to S-AMF:

-   -   Namf_Communication_CreateUEContext Response (N2 information        necessary for S-AMF to send Handover Command to S-RAN including        Target to Source transparent container, PDU Sessions failed to        be setup list, N2 SM information (N3 DL forwarding        Information)).    -   AMF supervises the Nsmf_PDUSession_UpdateSMContext Response        message from the involved SMFs. At expiry of the maximum wait        time or when all Nsmf_PDUSession_UpdateSMContext Response        messages are received, T-AMF sends the        Namf_Communication_CreateUEContext Response to the S-AMF.    -   [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE:        If the S-AMF (source AMF) has identified old NF IDs (e.g. SMF        IDs) in step 3, the T-AMF (target AMF) shall indicate back        whether the old NF IDs (e.g. SMF IDs) are being re-used by the        target AMF or whether new NF IDs are selected by the target        AMF.]    -   The Target to Source transport container is received from the        T-RAN. The N2 SM Information is received from the SMF in step        11f.

FIG. 9 illustrates the 4.9.1.3.3 Execution Phase. In support of theembodiments, Step 6a of the Preparation Phase may be updated to includethe following:

-   -   6a. [Conditional] T-AMF to S-AMF:        Namf_Communication_N2InfoNotify.    -   The T-AMF notifies to the S-AMF about the N2 handover notify        received from the T-RAN by invoking the        Namf_Communication_N2InfoNotify.    -   [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE:        If the S-AMF has provided selected NF IDs (e.g. PCF ID, SMSF        IDs, and the like) in preparation phase step 3, the new AMF        shall indicate back if the NF IDs are re-used by the new AMF or        new NF IDs are selected/used by the new AMF.]

A timer in S-AMF is started to supervise when resources in S-RAN shallbe release.

Step 14a may also be updated in the following manner:

-   -   14a. S-AMF to S-NG-RAN: UE Context Release Command ( )    -   After the timer in step 6a expires, the S-AMF sends UE Context        Release Command.    -   [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE:        The S-AMF also invokes the Nsmf_PDUSession_ReleaseSMContext        service operation to release the resource in SMF, in case an SMF        change is indicated in step 12 of the preparation phase.]    -   14b. S-NG-RAN to S-AMF: UE Context Release Complete Q.    -   The source NG-RAN releases its resources related to the UE and        responds with a UE Context Release Complete 0 message.

FIG. 10 illustrates 5.1.1.1.1 and 4.2.2.2.2 General Registrationprocedure, either for CM-IDLE mode mobility or CM-CONNECTED modemobility.

Step 5. [Conditional] old AMF to new AMF: Response toNamf_Communication_UEContextTransfer (SUPI, UE Context in AMF (as perTable 5.2.2.2.2-1)) or UDSF to new AMF: Nudsf_Unstructured DataManagement_Query( ).

-   -   If the UDSF was queried in step 4, the UDSF responds to the new        AMF for the Nudsf_Unstructured Data Management_Query invocation        with the related contexts including established PDU Sessions,        the old AMF includes SMF information DNN, S-NSSAI(s) and PDU        Session ID, active NGAP UE-TNLA bindings to N3IWF, the old AMF        includes information about the NGAP UE-TNLA bindings. If the Old        AMF was queried in step 4, Old AMF responds to the new AMF for        the Namf_Communication_UEContextTransfer invocation by including        the UE's SUPI and UE Context.    -   If old AMF holds information about established PDU Session(s),        the old AMF includes SMF information, DNN(s), S-NSSAI(s) and PDU        Session ID(s).    -   If old AMF holds information about active NGAP UE-TNLA bindings        to N3IWF, the old AMF includes information about the NGAP        UE-TNLA bindings.    -   If old AMF fails the integrity check of the Registration Request        NAS message, the old AMF shall indicate the integrity check        failure.    -   If old AMF holds information about AM Policy Association, the        old AMF includes the information about the AM Policy Association        including the policy control request trigger and PCF ID. In the        roaming case, V-PCF ID and H-PCF ID are included.

In support of the embodiments, Step 10 may be updated to including thefollowing:

-   -   10. [Conditional] new AMF to old AMF:        Namf_Communication_RegistrationCompleteNotify ( ).    -   If the AMF has changed the new AMF notifies the old AMF that the        registration of the UE in the new AMF is completed by invoking        the Namf_Communication_RegistrationCompleteNotify service        operation.    -   If the authentication/security procedure fails, then the        Registration shall be rejected, and the new AMF invokes the        Namf_Communication_RegistrationCompleteNotify service operation        with a reject indication reason code towards the old AMF. The        old AMF continues as if the UE context transfer service        operation was never received.    -   If one or more of the S-NSSAIs used in the old Registration Area        cannot be served in the target Registration Area, the new AMF        determines which PDU Session cannot be supported in the new        Registration Area. The new AMF invokes the        Namf_Communication_RegistrationCompleteNotify service operation        including the rejected PDU Session ID and a reject cause (e.g.        the S-NSSAI becomes no longer available) towards the old AMF.        Then the new AMF modifies the PDU Session Status        correspondingly. The old AMF informs the corresponding SMF(s) to        locally release the UE's SM context by invoking the        Nsmf_PDUSession_ReleaseSMContext service operation.    -   [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE:        If the old AMF has provided selected/old NF IDs (e.g. PCF ID,        SMSF IDs, . . . ), the new AMF shall indicate if these NF IDs        are re-used by the new AMF or new NF IDs are selected by the new        AMF.]    -   See clause 5.2.2.2.3 for details of        Namf_Communication_RegistrationCompleteNotify service operation.

In support of the embodiments, Step 21 may be updated to include thefollowing:

-   -   21. [Conditional] old AMF to (V-)PCF: AMF-Initiated Policy        Association Termination.    -   If the old AMF previously initiated a Policy Association to the        PCF, and the old AMF did not transfer the [IN ONE EMBODIMENT,        THE INFORMATION MAY BE UPDATED TO INCLUDE: selected/old NF IDs,        e.g. PCF ID] to the new AMF (e.g. new AMF is in different PLMN),        the old AMF performs an AMF-initiated Policy Association        Termination procedure, as defined in clause 4.16.3.2, to delete        the association with the PCF [IN ONE EMBODIMENT, THE INFORMATION        MAY BE UPDATED TO INCLUDE: and release the resource in PCF.]    -   [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE:        If the source AMF transferred the selected/old NF IDs to the        target AMF, and the target AMF has indicated back in step 10 (or        step 6a in the execution phase of the N2 HO procedure) if the        selected/old NF IDs are re-used or if new NF IDs are selected by        the target AMF, the source AMF either performs local release of        the PCF or an AMF-initiated Policy Association Termination        procedure, as defined in clause 4.16.3.2, to delete the        association with the PCF.

FIG. 11 illustrates the 4.16.1.3-1: Policy Association Establishmentwith the old PCF procedure. In support of the embodiments, Steps 6a and6b may be added in the following manner.

AM Policy Association Establishment with the Old PCF

The procedure relates to the situation of AMF relocation without PCFchange in handover procedure and registration procedure.

-   -   [IN ONE EMBODIMENT, THE FOLLOWING STEPS MAY BE ADDED: Steps 6a,        6b, Based on provided NF (e.g. PCF) re-use or NF change        information from the new/target AMF (as specified in        Registration procedure or HO procedure), the old AMF may        initiate Policy Association Termination procedure, as defined in        clause 4.16.3.2, to delete the association with the PCF or may        only perform a local PCF release.]

FIG. 12 is a schematic block diagram of a network function node suitablefor implementing a source mobility management function or targetmobility management function according to some embodiments of thepresent disclosure. The network function node 1200, for example, may bea computing device or other processing device. As illustrated, thenetwork function node 1200 includes a control system 1202 that includesone or more processors 1204 (e.g., Central Processing Units (CPUs),Application Specific Integrated Circuits (ASICs), Field ProgrammableGate Arrays (FPGAs), and/or the like), memory 1206, and a networkinterface 1208. The one or more processors 1204 are also referred toherein as processing circuitry. In addition, the network function node1200 may, in some embodiments, include one or more radio units 1210 thateach include one or more transmitters 1212 and one or more receivers1214 coupled to one or more antennas 1216. The radio units 1210 may bereferred to or be part of radio interface circuitry. In someembodiments, the radio unit(s) 1210 is external to the control system1202 and connected to the control system 1202 via, e.g., a wiredconnection (e.g., an optical cable). However, in some other embodiments,the radio unit(s) 1210 and potentially the antenna(s) 1216 areintegrated together with the control system 1202. The one or moreprocessors 1204 operate to provide one or more functions of the networkfunction node 1200 as described herein. In some embodiments, thefunction(s) are implemented in software that is stored, e.g., in thememory 1206 and executed by the one or more processors 1204.

FIG. 13 is a schematic block diagram that illustrates a virtualizedembodiment of the network function node 1200 according to someembodiments of the present disclosure. This discussion is equallyapplicable to other types of network nodes. Further, other types ofnetwork nodes may have similar virtualized architectures.

As used herein, a “virtualized” radio access node is an implementationof the network function node 1200 in which at least a portion of thefunctionality of the network function node 1200 is implemented as avirtual component(s) (e.g., via a virtual machine(s) executing on aphysical processing node(s) in a network(s)). As illustrated, in thisexample, the network function node 1200 includes the control system 1202that includes the one or more processors 1204 (e.g., CPUs, ASICs, FPGAs,and/or the like), the memory 1206, the network interface 1208, the oneor more radio units 1210 that each include the one or more transmitters1212, and the one or more receivers 1214 coupled to the one or moreantennas 1216, as described above. The control system 1202 is connectedto the radio unit(s) 1210 via, for example, an optical cable or thelike. The control system 1202 is connected to one or more processingnodes 1300 coupled to or included as part of a network(s) 1302 via thenetwork interface 1208. Each processing node 1300 includes one or moreprocessors 1304 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory1306, and a network interface 1308.

In this example, functions 1310 of the network function node 1200described herein are implemented at the one or more processing nodes1300 or distributed across the control system 1202 and the one or moreprocessing nodes 1300 in any desired manner. In some particularembodiments, some or all of the functions 1310 of the network functionnode 1200 described herein are implemented as virtual componentsexecuted by one or more virtual machines implemented in a virtualenvironment(s) hosted by the processing node(s) 1300. As will beappreciated by one of ordinary skill in the art, additional signaling orcommunication between the processing node(s) 1300 and the control system1202 is used in order to carry out at least some of the desiredfunctions 1310. Notably, in some embodiments, the control system 1202may not be included, in which case the radio unit(s) 1210 communicatesdirectly with the processing node(s) 1300 via an appropriate networkinterface(s).

In some embodiments, a computer program including instructions which,when executed by at least one processor, causes the at least oneprocessor to carry out the functionality of the network function node1200 or a node (e.g., a processing node 1300) implementing one or moreof the functions 1310 of the network function node 1200 in a virtualenvironment according to any of the embodiments described herein isprovided. In some embodiments, a carrier comprising the aforementionedcomputer program product is provided. The carrier is one of anelectronic signal, an optical signal, a radio signal, or a computerreadable storage medium (e.g., a non-transitory computer readable mediumsuch as memory).

FIG. 14 is a schematic block diagram of the network function node 1200according to some other embodiments of the present disclosure. Thenetwork function node 1200 includes one or more modules 1402, each ofwhich is implemented in software. The module(s) 1402 provide thefunctionality of the network function node 1200 described herein, suchas that attributed to a target AMF or a source AMF.

FIG. 15 is a flowchart illustrating a method for a target mobilitymanagement function, such as a target AMF, in a core network tocommunicate NF utilization information with a source mobility managementfunction, such as a source AMF, during a change of mobility managementfunction according to one embodiment. The target mobility managementfunction receives at least one old NF identifier (ID) from the sourcemobility management function that corresponds to an old network function(NF) serving a user equipment (UE) (block 1500). The old NF maycomprise, for example, an old SMF, an old SMSF, an old PCF, or any otherNF. The target mobility management function determines to either use theat least one old NF ID or to use at least one new NF ID that correspondsto a new NF of a same NF type as the old NF (block 1502). The new NF maycomprise, for example, a new SMF, a new SMSF, a new PCF, or any otherNF. The target mobility management function communicates, to the sourcemobility management function, information that indicates to the sourcemobility management function whether the target mobility managementfunction uses the at least one old NF ID or uses the at least one new NFID (block 1504).

FIG. 16 is a flowchart illustrating a method implemented in a sourcemobility management function, such as a source AMF, in accordance withone embodiment. The source mobility management function sends, to thetarget mobility management function, such as a target AMF, at least oneold NF identifier (ID) that corresponds to an old network function (NF)serving a user equipment (UE) (block 1600). The old NF may comprise, forexample, an old SMF, an old SMSF, an old PCF, or any other NF. Thesource mobility management function receives, from the target mobilitymanagement function, information that indicates whether the targetmobility management function uses the at least one old NF ID or uses atleast one new NF ID that corresponds to a new NF serving the UE (block1602). The new NF may comprise, for example, a new SMF, a new SMSF, anew PCF, or any other NF.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include Digital Signal Processor (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as Read Only Memory (ROM),Random Access Memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

While processes in the figures may show a particular order of operationsperformed by certain embodiments of the present disclosure, it should beunderstood that such order is exemplary (e.g., alternative embodimentsmay perform the operations in a different order, combine certainoperations, overlap certain operations, etc.).

Some Embodiments

Some of the embodiments described above may be summarized in thefollowing itemized manner:

Item 1. A method for a target mobility management function entity in acore network to communicate network function (NF) utilizationinformation with a source mobility management function entity during achange of mobility management function entity, comprising:

receiving, by the target mobility management function entity, at leastone old NF identifier (ID) from the source mobility management functionentity that corresponds to an old NF entity serving a user equipment(UE);

determining to either use the at least one old NF ID or to use at leastone new NF ID that corresponds to a new NF entity of a same NF type asthe old NF entity; and

communicating, by the target mobility management function entity to thesource mobility management function entity, information that indicatesto the source mobility management function entity whether the targetmobility management function entity uses the at least one old NF ID oruses the at least one new NF ID.

Item 2. The method of item 1 wherein the NF entities comprise one ormore of a short message service function (SMSF) entity, a policy controlfunction (PCF) entity, and a session management function (SMF) entity.

Item 3. The method of item 1 wherein the target mobility managementfunction entity comprises a target access and mobility managementfunction (AMF) entity, and wherein the source mobility managementfunction entity comprises a source AMF entity.

Item 4. The method of item 3 wherein communicating the information thatindicates to the source mobility management function entity whether thetarget mobility management function entity uses the at least one old NFID or uses the at least one new NF ID comprises:

sending, by the target AMF entity to the source AMF entity, aNamf_Communication_CreateUEContext response that indicates to the sourceAMF entity whether the target AMF entity uses the at least one old NF IDor uses the at least one new NF ID.

Item 5. The method of item 4 further comprising generating theNamf_Communication_CreateUEContext response while invoking aNamf_Communication_CreateUEContext service operation.

Item 6. The method of item 3 wherein communicating the information thatindicates to the source AMF entity whether the target AMF entity usesthe at least one old NF ID or uses the at least one new NF ID comprises:

receiving, by the target AMF entity, a handover notify from a radioaccess node (RAN); and

invoking, by the target AMF entity in response to the handover notify, aNamf_Communication_N2InfoNotify service operation that indicates to thesource AMF entity whether the target AMF entity uses the at least oneold NF ID or uses the at least one new NF ID.

Item 7. The method of item 3 wherein communicating the information thatindicates to the source AMF entity whether the target AMF entity usesthe at least one old NF ID or uses the at least one new NF ID comprises:

invoking, by the target AMF entity, aNamf_Communication_RegistrationCompleteNotify service operation thatindicates to the source AMF entity whether the target AMF entity usesthe at least one old NF ID or uses the at least one new NF ID.

Item 8. The method of item 1 wherein determining to either use the atleast one old NF ID or to use the at least one new NF ID thatcorresponds the new NF entity of the same NF type as the old NF entitycomprises performing a NF service discover function to determine toeither use the at least one old NF ID or to use the at least one new NFID that corresponds to the new NF entity of the same NF type as the oldNF entity.Item 9. A method for a source mobility management function entity in acore network to receive network function (NF) utilization informationfrom a target mobility management function entity during a change ofmobility management function entity, comprising:

sending, by the source mobility management function entity to the targetmobility management function entity, at least one old NF identifier (ID)that corresponds to an old NF entity serving a user equipment (UE); and

receiving, by the source mobility management function entity from thetarget mobility management function entity, information that indicateswhether the target mobility management function entity uses the at leastone old NF ID or uses at least one new NF ID that corresponds to a newNF entity serving the UE.

Item 10. The method of item 9 wherein the NF entities comprise one ormore of a short message service function (SMSF) entity, a policy controlfunction (PCF) entity, and a session management function (SMF) entity.

Item 11. The method of item 9 wherein the target mobility managementfunction entity comprises a target access and mobility managementfunction (AMF) entity, and wherein the source mobility managementfunction entity comprises a source AMF entity.

Item 12. The method of item 11 wherein the information indicates thatthe target AMF entity is using a new session management function (SMF)ID, and further comprising:

invoking a Nsmf_PDUSession_ReleaseSMContext service operation, by thesource AMF entity toward an old SMF entity, to release an existingsession management (SM) context in the old SMF entity.

Item 13. The method of item 11 wherein the information indicates thatthe target AMF entity is using an old SMF ID, and further comprising:

deleting, by the source AMF entity locally, to release an existingsession management (SM) context in the source AMF entity.

Item 14. The method of item 11 wherein the information indicates thatthe target AMF entity is using an old policy control function (PCF) ID,and further comprising:

performing, by the source AMF entity, a local release of an old PCF thatcorresponds to the old PCF ID.

Item 15. The method of item 14 wherein the information indicates thatthe target AMF entity is utilizing a new PCF ID, and further comprising:

-   -   sending, by the source AMF entity to a PCF entity, a        Npcf_AMPolicyControl_Delete service operation.        Item 16. The method of item 11 wherein the information indicates        that the target AMF entity is using an old SMSF ID and further        comprising:

performing, by the source AMF entity, a local release of an associationcontext of an old SMSF entity that corresponds to the old SMSF ID.

Item 17. The method of item 11 wherein the information indicates thatthe target AMF entity is utilizing a new SMSF ID and further comprising:

sending, by the source AMF entity to an old SMSF entity, aNsmsf_SMService_Deactivate service operation to trigger a release of UEContext for SMS on the old SMSF entity.

Item 18. A target mobility management function entity for communicatingnetwork function (NF) utilization information with a source mobilitymanagement function entity during a change of mobility managementfunction entity, the target mobility management function entitycomprising:

one or more processors; and

memory storing instructions executable by the one or more processors,whereby the target mobility management function entity is operable toperform the method of:

-   -   receiving, by the target mobility management function entity, at        least one old NF identifier (ID) from the source mobility        management function entity that corresponds to an old NF entity        serving a user equipment (UE);    -   determining to either use the at least one old NF ID or to use        at least one new NF ID that corresponds to a new NF entity of a        same NF type as the old NF entity; and    -   communicating, by the target mobility management function entity        to the source mobility management function entity, information        that indicates to the source mobility management function entity        whether the target mobility management function entity uses the        at least one old NF ID or uses the at least one new NF ID.        Item 19. A source mobility management function entity for        receiving network function (NF) utilization information from a        target mobility management function entity during a change of        mobility management function entity, the source mobility        management function entity comprising:

one or more processors; and

memory storing instructions executable by the one or more processors,whereby the source mobility management function entity is operable toperform the method of:

-   -   sending, by the source mobility management function entity to        the target mobility management function entity, at least one old        NF identifier (ID) that corresponds to an old NF entity serving        a user equipment (UE); and    -   receiving, by the source mobility management function entity        from the target mobility management function entity, information        that indicates whether the target mobility management function        entity uses the at least one old NF ID or uses at least one new        NF ID that corresponds to a new NF entity serving the UE.        Item 20. A non-transitory computer readable medium storing        software instructions that, when executed by one or more        processors of a network entity for performing a method for a        source mobility management function entity for receiving network        function (NF) utilization information from a target mobility        management function entity during a change of mobility        management function entity, cause the network entity to perform        the method of:    -   sending, by the source mobility management function entity to        the target mobility management function entity, at least one old        NF identifier (ID) that corresponds to an old NF entity serving        a user equipment (UE); and    -   receiving, by the source mobility management function entity        from the target mobility management function entity, information        that indicates whether the target mobility management function        entity uses the at least one old NF ID or uses at least one new        NF ID that corresponds to a new NF entity serving the UE.        Item 21. A computer program comprising instructions which, when        executed by at least one processor of a network entity, cause        the at least one processor to perform the method of:    -   sending, by a source mobility management function entity to a        target mobility management function entity, at least one old        network function (NF) identifier (ID) that corresponds to an old        NF entity serving a user equipment (UE); and    -   receiving, by the source mobility management function entity        from the target mobility management function entity, information        that indicates whether the target mobility management function        entity uses the at least one old NF ID or uses at least one new        NF ID that corresponds to a new NF entity serving the UE.        Item 22. A carrier comprising the computer program of item 21,        wherein the carrier is one of an electronic signal, an optical        signal, a radio signal, or a computer readable storage medium.        Item 23. A non-transitory computer readable medium storing        software instructions that, when executed by one or more        processors of a network entity for performing a method for        communicating network function (NF) utilization information with        a source mobility management function entity during a change of        mobility management function entity, cause the network entity to        perform the method of:

receiving at least one old NF identifier (ID) from the source mobilitymanagement function entity that corresponds to an old NF serving a userequipment (UE);

determining to either use the at least one old NF ID or to use at leastone new NF ID that corresponds to a new NF entity of a same NF entitytype as the old NF entity; and

communicating, to the source mobility management function entity,information that indicates to the source mobility management functionentity whether the target mobility management function entity uses theat least one old NF ID or uses the at least one new NF ID.

Item 24. A computer program comprising instructions which, when executedby at least one processor of a network entity, cause the at least oneprocessor to perform the method of:

receiving, by a target mobility management function entity, at least oneold network function (NF) identifier (ID) from a source mobilitymanagement function entity that corresponds to an old NF entity servinga user equipment (UE);

determining to either use the at least one old NF ID or to use at leastone new NF ID that corresponds to a new NF entity of a same NF entitytype as the old NF entity; and

communicating, by the target mobility management function entity to thesource mobility management function entity, information that indicatesto the source mobility management function entity whether the targetmobility management function entity uses the at least one old NF ID oruses the at least one new NF ID.

Item 25. A carrier comprising the computer program of item 24, whereinthe carrier is one of an electronic signal, an optical signal, a radiosignal, or a computer readable storage medium.

ABBREVIATIONS

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   1×RTT CDMA2000 1× Radio Transmission Technology    -   2G Second Generation    -   3G Third Generation    -   3GPP Third Generation Partnership Project    -   4G Fourth Generation    -   5G Fifth Generation    -   ABS Almost Blank Subframe    -   AC Alternating Current    -   AF Application Function    -   AMF Access and Mobility Management Function    -   AN Access Network    -   AP Access Point    -   ARQ Automatic Repeat Request    -   ASIC Application Specific Integrated Circuit    -   ATM Asynchronous Transfer Mode    -   AUSF Authentication Server Function    -   AWGN Additive White Gaussian Noise    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BS Base Station    -   BSC Base Station Controller    -   BTS Base Transceiver Station    -   BW Bandwidth    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control Channel    -   CD Compact Disk    -   CDMA Code Division Multiple Access    -   CGI Cell Global Identity    -   CIR Channel Impulse Response    -   COTS Commercial Off-the-Shelf    -   CP Cyclic Prefix    -   CPE Customer Premise Equipment    -   CPICH Common Pilot Channel    -   CPICH Ec/No Common Pilot Channel received energy per chip        divided by the power density in the band    -   CPU Central Processing Unit    -   CQI Channel Quality Information    -   C-RNTI Cell Radio Network Temporary Identifier    -   CSI Channel State Information    -   CSI-RS Channel State Information Reference Signal    -   D2D Device-to-Device    -   DAS Distributed Antenna System    -   DC Direct Current    -   DCCH Dedicated Control Channel    -   DIMM Dual In-Line Memory Module    -   DL Downlink    -   DM Demodulation    -   DMRS Demodulation Reference Signal    -   DN Data Network    -   DRX Discontinuous Reception    -   DSP Digital Signal Processor    -   DTX Discontinuous Transmission    -   DTCH Dedicated Traffic Channel    -   DUT Device Under Test    -   DVD Digital Video Disk    -   E-CID Enhanced Cell Identifier (positioning method)    -   EEPROM Electrically Erasable Programmable Read Only Memory    -   ECGI Evolved Cell Global Identifier    -   eMTC Enhanced Machine-Type Communication    -   eNB Enhanced or Evolved Node B    -   ePDCCH Enhanced Physical Downlink Control Channel    -   EPROM Erasable Programmable Read Only Memory    -   E-SMLC Enhanced Serving Mobile Location Center    -   E-UTRA Evolved Universal Terrestrial Radio Access    -   E-UTRAN Evolved Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplexing    -   FFS For Further Study    -   FPGA Field Programmable Gate Array    -   GERAN Global System for Mobile (GSM) Communications Enhanced        Data Rates for GSM Evolution Radio Access Network    -   GHz Gigahertz    -   gNB New Radio Base Station    -   GNSS Global Navigation Satellite System    -   GPS Global Positioning System    -   GSM Global System for Mobile Communications    -   HARQ Hybrid Automatic Repeat Request    -   HDDS Holographic Digital Data Storage    -   HD-DVD High-Definition Digital Versatile Disc    -   HO Handover    -   HRPD High Rate Packet Data    -   HSPA High Speed Packet Access    -   I/O Input and Output    -   IoT Internet of Things    -   IP Internet Protocol    -   LAN Local Area Network    -   LEE Laptop Embedded Equipment    -   LME Laptop Mounted Equipment    -   LOS Line of Sight    -   LPP Long Term Evolution Positioning Protocol    -   LTE Long Term Evolution    -   M2M Machine-to-Machine    -   MAC Medium Access Control    -   MANO Management and Orchestration    -   MBMS Multimedia Broadcast Multicast Services    -   MBSFN Multimedia Broadcast Multicast Service Single Frequency        Network    -   MCE Multi-Cell/Multicast Coordination Entity    -   MDT Minimization of Drive Tests    -   MIB Master Information Block    -   MIMO Multiple Input Multiple Output    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   MSR Multi-Standard Radio    -   MTC Machine Type Communication    -   NB-IoT Narrowband Internet of Things    -   NEF Network Exposure Function    -   NF Network Function    -   NFV Network Function Virtualization    -   NIC Network Interface Controller    -   NPDCCH Narrowband Physical Downlink Control Channel    -   NR New Radio    -   NRF Network Repository Function    -   NSSF Network Slice Selection Function    -   O&M Operation and Maintenance    -   OCNG Orthogonal Frequency Division Multiple Access Channel Noise        Generator    -   OFDM Orthogonal Frequency Division Multiplexing    -   OFDMA Orthogonal Frequency Division Multiple Access    -   OSS Operations Support System    -   OTDOA Observed Time Difference of Arrival    -   OTT Over-the-Top    -   PBCH Physical Broadcast Channel    -   P-CCPCH Primary Common Control Physical Channel    -   PCell Primary Cell    -   PCF Policy Control Function    -   PCFICH Physical Control Format Indicator Channel    -   PDA Personal Digital Assistant    -   PDCCH Physical Downlink Control Channel    -   PDP Power Delay Profile    -   PDSCH Physical Downlink Shared Channel    -   P-GW Packet Data Network Gateway    -   PHICH Physical Hybrid Automatic Repeat Request Indicator Channel    -   PLMN Public Land Mobile Network    -   PMI Precoder Matrix Indicator    -   PRACH Physical Random Access Channel    -   PRB Physical Resource Block    -   PROM Programmable Read Only Memory    -   PRS Positioning Reference Signal    -   PSS Primary Synchronization Signal    -   PSTN Public Switched Telephone Networks    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   QoS Quality of Service    -   RACH Random Access Channel    -   RAID Redundant Array of Independent Disks    -   RAM Random Access Memory    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RE Resource Element    -   RF Radio Frequency    -   RLM Radio Link Monitoring    -   RNC Radio Network Controller    -   RNTI Radio Network Temporary Identifier    -   ROM Read Only Memory    -   RRC Radio Resource Control    -   RRH Remote Radio Head    -   RRM Radio Resource Management    -   RRU Remote Radio Unit    -   RS Reference Signal    -   RSCP Received Signal Code Power    -   RSRP Reference Symbol Received Power/Reference Signal Received        Power    -   RSRQ Reference Symbol Received Quality/Reference Signal Received        Quality    -   RSSI Received Signal Strength Indicator    -   RSTD Reference Signal Time Difference    -   RTT Round Trip Time    -   RUIM Removable User Identity    -   SCEF Service Capability Exposure Function    -   SCell Secondary Cell    -   SCH Synchronization Channel    -   SDRAM Synchronous Dynamic Random Access Memory    -   SDU Service Data Unit    -   SFN System Frame Number    -   S-GW Serving Gateway    -   SI System Information    -   SIB System Information Block    -   SIM Subscriber Identity Module    -   SMF Session Management Function    -   SMSF Short Message Service Function    -   SNR Signal to Noise Ratio    -   SOC System on a Chip    -   SON Self-Organizing Network    -   SONET Synchronous Optical Networking    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   TCP Transmission Control Protocol    -   TDD Time Division Duplexing    -   TDOA Time Difference of Arrival    -   TOA Time of Arrival    -   TPMI Transmit Precoding Matrix Indicator    -   TRP Transmission/Reception Point    -   TSS Tertiary Synchronization Signal    -   TTI Transmission Time Interval    -   UDM Unified Data Management    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunications System    -   USB Universal Serial Bus    -   USIM Universal Subscriber Identity Module    -   UTDOA Uplink Time Difference of Arrival    -   UTRA Universal Terrestrial Radio Access    -   UTRAN Universal Terrestrial Radio Access Network    -   V2I Vehicle-to-Infrastructure    -   V2V Vehicle-to-Vehicle    -   V2X Vehicle-to-Everything    -   VMM Virtual Machine Monitor    -   VNE Virtual Network Element    -   VNF Virtual Network Function    -   VoIP Voice over Internet Protocol    -   WAN Wide Area Network    -   WCDMA Wideband Code Division Multiple Access    -   WD Wireless Device    -   WiMax Worldwide Interoperability for Microwave Access    -   WLAN Wireless Local Area Network

The invention claimed is:
 1. A non-transitory computer readable mediumcomprising instructions executable by processing circuitry of a networknode that implements a target Access and mobility Management Function,AMF, entity in a core network for communicating network function, NF,utilization information with a source AMF entity during a change of AMFentity from the source AMF entity to the target AMF entity, whereby thenetwork node is operable to: receive, by the target AMF entity, at leastone old NF identifier, ID, from the source AMF entity that correspondsto an old NF entity serving a user equipment, UE; determine to eitheruse the at least one old NF ID or to use at least one new NF ID thatcorresponds to a new NF entity of a same NF type as the old NF entity;and communicate, by the target AMF entity to the source AMF entity,information that indicates to the source AMF entity whether the targetAMF entity uses the at least one old NF ID or uses the at least one newNF ID.
 2. The non-transitory computer readable medium of claim 1 whereinthe new and old NF entities comprise one or more of a short messageservice function, SMSF, entity, a policy control function, PCF, entity,and a session management function, SMF, entity.
 3. The non-transitorycomputer readable medium of claim 1 wherein, in order to communicate theinformation that indicates to the source AMF entity whether the targetAMF entity uses the at least one old NF ID or uses the at least one newNF ID, the network node via execution of the instructions by theprocessing circuitry is operable to: send, by the target AMF entity tothe source AMF entity, a Namf_Communication_CreateUEContext responsethat indicates to the source AMF entity whether the target AMF entityuses the at least one old NF ID or uses the at least one new NF ID. 4.The non-transitory computer readable medium of claim 3 wherein, viaexecution of the instructions by the processing circuitry, the networknode is further operable to generate theNamf_Communication_CreateUEContext response while invoking aNamf_Communication_CreateUEContext service operation.
 5. Thenon-transitory computer readable medium of claim 1 wherein, in order tocommunicate the information that indicates to the source AMF entitywhether the target AMF entity uses the at least one old NF ID or usesthe at least one new NF ID, the network node via execution of theinstructions by the processing circuitry is operable to: receive, by thetarget AMF entity, a handover notify from a radio access node, RAN; andinvoke, by the target AMF entity in response to the handover notify, aNamf_Communication_N2InfoNotify service operation that indicates to thesource AMF entity whether the target AMF entity uses the at least oneold NF ID or uses the at least one new NF ID.
 6. The non-transitorycomputer readable medium of claim 1 wherein, in order to communicate theinformation that indicates to the source AMF entity whether the targetAMF entity uses the at least one old NF ID or uses the at least one newNF ID, the network node via execution of the instructions by theprocessing circuitry is operable to: invoke, by the target AMF entity, aNamf_Communication_RegistrationCompleteNotify service operation thatindicates to the source AMF entity whether the target AMF entity usesthe at least one old NF ID or uses the at least one new NF ID.
 7. Thenon-transitory computer readable medium of claim 1 wherein, in order todetermine to either use the at least one old NF ID or to use the atleast one new NF ID that corresponds the new NF entity of the same NFtype as the old NF entity, the network node via execution of theinstructions by the processing circuitry is operable to perform a NFservice discover function to determine to either use the at least oneold NF ID or to use the at least one new NF ID that corresponds to thenew NF entity of the same NF type as the old NF entity.
 8. Anon-transitory computer readable medium comprising instructionsexecutable by processing circuitry of a network node that implements asource Access and Mobility Management Function, AMF, entity (old AMF) ina core network for receiving network function, NF, utilizationinformation from a target AMF entity (new AMF) during a change of AMFentity from the source AMF entity to the target AMF entity, whereby thenetwork node is operable to: send, by the source AMF entity to thetarget AMF entity, at least one old NF identifier, ID, that correspondsto an old NF entity serving a user equipment, UE; and receive, by thesource AMF entity from the target AMF entity, information that indicateswhether the target AMF entity uses the at least one old NF ID or uses atleast one new NF ID that corresponds to a new NF entity serving the UE.9. The non-transitory computer readable medium of claim 8 wherein thenew and old NF entities comprise one or more of a short message servicefunction, SMSF, entity, a policy control function, PCF, entity, and asession management function, SMF, entity.
 10. The non-transitorycomputer readable medium of claim 8 wherein the information indicatesthat the target AMF entity is using a new session management function,SMF, ID, and via execution of the instructions via the processingcircuitry, the network node is further operable to: invoke aNsmf_PDUSession_ReleaseSMContext service operation, by the source AMFentity toward an old SMF entity, to release an existing sessionmanagement, SM, context in the old SMF entity.
 11. The non-transitorycomputer readable medium of claim 8 wherein the information indicatesthat the target AMF entity is using an old session management function,SMF, ID, and via execution of the instructions by the processingcircuitry, the network node is further operable to: delete, by thesource AMF entity locally, to release an existing session management,SM, context in the source AMF entity.
 12. The non-transitory computerreadable medium of claim 8 wherein the information indicates that thetarget AMF entity is using an old policy control function, PCF, ID, andvia execution of the instructions by the processing circuitry, thenetwork node is further operable to: perform, by the source AMF entity,a local release of an old PCF entity that corresponds to the old PCF ID.13. The non-transitory computer readable medium of claim 12 wherein theinformation indicates that the target AMF entity is utilizing a new PCFID, and via execution of the instructions by the processing circuitry,the network node is further operable to: send, by the source AMF entityto a PCF entity, a Npcf_AMPolicyControl_Delete service operation. 14.The non-transitory computer readable medium of claim 8 wherein theinformation indicates that the target AMF entity is using an old shortmessage service function, SMSF, ID and, via execution of theinstructions by the processing circuitry, the network node is furtheroperable to: perform, by the source AMF entity, a local release of anassociation context of an old SMSF entity that corresponds to the oldSMSF ID.
 15. The non-transitory computer readable medium of claim 8wherein the information indicates that the target AMF entity isutilizing a new short message service function, SMSF, ID and, viaexecution of the instructions by the processing circuitry, the networknode is further operable to: send, by the source AMF entity to an oldSMSF entity, a Nsmsf_SMService_Deactivate service operation to trigger arelease of UE Context for session management function, SMS, on the oldSMSF entity.